Skip to content

chore: drop alpha warnings and stay on prerelease version - #8

Merged
mishamilovidov merged 2 commits into
mainfrom
RUNNER-9680-remove-alpha
Jul 29, 2026
Merged

chore: drop alpha warnings and stay on prerelease version#8
mishamilovidov merged 2 commits into
mainfrom
RUNNER-9680-remove-alpha

Conversation

@mishamilovidov

@mishamilovidov mishamilovidov commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Bump the version from 0.1.0a9 to 0.1.0a10. This stays a PEP 440 prerelease, it is not a GA release.
  • Remove the alpha status badge and warning block from the README, and drop --pre from the install snippet.
  • Drop --pre from the RELEASING.md install verification step and update the example version bump command.
  • Delete the RELEASING.md note that claimed pip install aio-lib-sandbox will not pick up the package without --pre.

Related Issues

Notes

  • The --pre flag was never required. pip only excludes prereleases when a stable release exists to fall back to, and every version ever published here is a prerelease, so a plain pip install aio-lib-sandbox already resolves the newest. Verified against pip 23 and pip 26, plain and pinned.
  • The deleted RELEASING.md note was therefore wrong on its stated reason. Its actual guidance, keep the prerelease suffix until the API is stable, still holds and this PR follows it.
  • Unlike npm, PyPI has no dist-tag concept, so there is no stale pointer to repair here. This change is docs and version only.
  • The package stays on a PEP 440 prerelease version string deliberately. This removes the user facing alpha noise without claiming API stability.

Bumps the SDK to 1.0.0 and drops all alpha-specific guidance now that the API is stable for general availability. Removes the alpha status badge, warning block, and --pre install instructions from the docs so users can install the package normally.

RUNNER-9680
@mishamilovidov
mishamilovidov force-pushed the RUNNER-9680-remove-alpha branch from c2a8da5 to d6fbace Compare July 22, 2026 18:11
@codecov

codecov Bot commented Jul 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@mishamilovidov
mishamilovidov marked this pull request as ready for review July 22, 2026 20:50

@MichaelGoberling MichaelGoberling left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with the same naming Q as on the JS lib

adobe/aio-lib-sandbox#8 (comment)

@mishamilovidov

Copy link
Copy Markdown
Contributor Author

note: I have added the DO NOT MERGE label on this change since internal discussions are ongoing RE the implications of taking the sandbox SDKs out of alpha. Once those discussions settle, I'll update this PR.

The team decided not to go GA yet, so this reverts the previous commit's bump to 1.0.0 and keeps the SDK on a PEP 440 prerelease version, 0.1.0a10, while still removing the user facing alpha warning badge and the now redundant --pre install flag from the docs. Every release of this package has been a prerelease, and pip already resolves the latest prerelease when no stable release exists to fall back to, so dropping --pre does not change install behavior or imply a stable release. Also fixes RELEASING.md so the example version bump command no longer instructs a future releaser to cut a 1.0.0 release.

RUNNER-9680
@mishamilovidov mishamilovidov changed the title chore: remove alpha designation for 1.0.0 ga chore: drop alpha warnings and stay on prerelease version Jul 29, 2026
@mishamilovidov

Copy link
Copy Markdown
Contributor Author

Approved with the same naming Q as on the JS lib

adobe/aio-lib-sandbox#8 (comment)

This has been resolved. See my response here.

@mishamilovidov

Copy link
Copy Markdown
Contributor Author

note: This PR changed direction from its original intent. It no longer takes the SDK GA.

The internal discussions referenced in my note above have settled: we are keeping both this SDK and the JS SDK on prerelease versions rather than cutting a GA release. The open App Builder product questions that motivated the original alpha designation have not fully settled, and both SDKs remain branded and owned by App Builder, so a GA claim would be premature. See this thread on the JS PR for the discussion.

What this PR still does:

  • Removes the user facing alpha noise: the status badge and warning block in the README.
  • Drops --pre from the install snippet, the RELEASING.md verification step, and the example version command. The flag was never actually required: pip only excludes prereleases when a stable release exists to fall back to, and every release of this package is a prerelease, so a plain pip install aio-lib-sandbox already resolves the newest version.
  • Deletes the RELEASING.md note claiming pip install aio-lib-sandbox will not pick up the package without --pre. That was never true for this package: pip only excludes prereleases when a stable release exists to fall back to, and every version ever published here is a prerelease. Verified against pip 23 and pip 26, plain and pinned. The note's actual guidance, keep the prerelease suffix until the API is stable, still holds and this PR follows it.

What it deliberately does not do:

  • The package stays on a PEP 440 prerelease version string (0.1.0a10). This is a prerelease, not a GA release, and it makes no claim of API stability.
  • No rename. These remain the App Builder SDKs.

Unlike npm, PyPI has no dist-tag concept, so there is no stale pointer to repair on this side. This change is docs and version only.

The GA work moves to a separate effort; we are planning to fork these into a set of Runtime/FaaSt owned SDKs, renamed to something not tied specifically to App Builder, and that fork is what will be shaped as the "sandbox SDK GA".

@mishamilovidov
mishamilovidov merged commit df537d6 into main Jul 29, 2026
6 checks passed
@mishamilovidov
mishamilovidov deleted the RUNNER-9680-remove-alpha branch July 29, 2026 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants